Managing devices through use of blocks of operational profiles

ABSTRACT

Aspects of the subject disclosure may include, for example, identifying a plurality of operational profiles that are to be shared by a plurality of devices; assigning a first operational profile of the plurality of operational profiles to a first device of the plurality of devices; assigning a second operational profile of the plurality of operational profiles to a second device of the plurality of devices; facilitating provision of the first operational profile on the first device; and facilitating provision of the second operational profile on the second device. Other embodiments are disclosed.

CROSS REFERENCE TO RELATED APPLICATION(S)

This application is a continuation of U.S. patent application Ser. No. 16/678,926, filed on Nov. 8, 2019. All sections of the aforementioned application(s) and/or patent(s) are incorporated herein by reference in their entirety.

FIELD OF THE DISCLOSURE

The subject disclosure relates to managing devices through use of blocks of operational profiles. In various examples, the managed devices can comprise one or more mobile communication devices (e.g. mobile telephones, tablets, netbook computers, notebook computers), one or more computing devices, one or more vehicles, one or more Internet of Things (IoT) devices (e.g., water meters, electric meters, smart light bulbs, sensors), or any combination thereof.

BACKGROUND

Communication devices can be registered on mobile networks to be provided services, such as location, voice, video, messaging, and data communication services. These communication devices can include mobile devices, sensors, power meters and other Internet of Things (IoT) devices. In the event that a subscription for services has expired for the communication devices, renewal of the subscription to one mobile network or migrating to another mobile network can be a manual labor intensive process including manual provisioning the communication devices with new registration information to renew subscription of services on one mobile network or migrating to another mobile network.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings, which are not necessarily drawn to scale, and wherein:

FIG. 1 is a block diagram illustrating an exemplary, non-limiting embodiment of a communications network in accordance with various aspects described herein.

FIGS. 2A-2D are block diagrams illustrating example, non-limiting embodiments of systems functioning within the communication network of FIG. 1 in accordance with various aspects described herein.

FIGS. 2E-2F depict illustrative embodiments of methods in accordance with various aspects described herein.

FIG. 2G is a block diagram illustrating an example, non-limiting embodiment of a system functioning within the communication network of FIG. 1 in accordance with various aspects described herein.

FIGS. 2H-2J depict illustrative embodiments of methods in accordance with various aspects described herein.

FIG. 3 is a block diagram illustrating an example, non-limiting embodiment of a virtualized communication network in accordance with various aspects described herein.

FIG. 4 is a block diagram of an example, non-limiting embodiment of a computing environment in accordance with various aspects described herein.

FIG. 5 is a block diagram of an example, non-limiting embodiment of a mobile network platform in accordance with various aspects described herein.

FIG. 6 is a block diagram of an example, non-limiting embodiment of a communication device in accordance with various aspects described herein.

DETAILED DESCRIPTION

The subject disclosure describes, among other things, illustrative embodiments in which a mobile communication device performs the following: identifying a plurality of operational profiles that are to be shared by a plurality of devices; assigning a first operational profile of the plurality of operational profiles to a first device of the plurality of devices; assigning a second operational profile of the plurality of operational profiles to a second device of the plurality of devices; facilitating provision of the first operational profile on the first device; and facilitating provision of the second operational profile on the second device.

The subject disclosure describes, among other things, illustrative embodiments in which a mobile communication device performs the following: receiving, from a server that is part of a communications network operated by a network provider, an identification of a plurality of operational profiles, each operational profile being assigned to a different Internet of Things (IoT) device of a plurality of IoT devices; providing, based upon each operational profile being assigned to a different IoT device, a first operational profile of the plurality of operational profiles to a first IoT device of the plurality of IoT devices; and providing, based upon each operational profile being assigned to a different IoT device, a second operational profile of the plurality of operational profiles to a second IoT device of the plurality of IoT devices.

The subject disclosure describes, among other things, illustrative embodiments in which a method comprises the following: identifying, by a processing system of a mobile communication device including a processor, a plurality of operational profiles that are to be shared by a plurality of Internet of Things (IoT) devices; providing by the processing system, based upon the identifying, a first operational profile of the plurality of operational profiles to a first IoT device of the plurality of IoT devices, the providing of the first operational profile enabling use by the first IoT device of the first operational profile; and providing by the processing system, based upon the identifying, a second operational profile of the plurality of operational profiles to the first IoT device, the providing of the second operational profile enabling the first IoT device to send to a second IoT device the second operational profile for use by the second IoT device.

The subject disclosure describes, among other things, illustrative embodiments in which a method comprises the following: identifying, by a server (e.g., a server of a communications network operated by a network provider), a plurality of operational profiles that are to be shared by a plurality of devices; providing by the server, based upon the identifying, a first operational profile of the plurality of operational profiles to a first device of the plurality of device (the first operational profile can be provided to the first device directly from the server and/or indirectly from the server via an intermediary device (e.g., a mobile communication device)); and providing by the server, based upon the identifying, a second operational profile of the plurality of operational profiles to the second device (the second operational profile can be provided to the second device directly from the server and/or indirectly from the server via an intermediary device (e.g., a mobile communication device).

The subject disclosure describes, among other things, illustrative embodiments for determining a first subscription associated with a communication device has expired, the first subscription is for a first group of services for a mobile network. Further embodiments can include receiving, over the mobile network, a first registration request from the communication device, detecting, over the mobile network, a bootstrap profile on the communication device, and providing, over the mobile network, according to the bootstrap profile, limited services to the communication device to subscribe to a second subscription for a second group of services. Additional embodiments can include obtaining subscription information for the second subscription for the second group of services, adjusting, over the mobile network, an operational profile on the communication device according to the subscription information resulting in an adjusted operational profile, and receiving, over the mobile network, a second registration request for the communication device according to the adjusted operation profile. Also, embodiments can include registering the communication device according to the adjusted operational profile, and providing, over the mobile network, the second group of services to the communication device according to the adjusted operational profile. Other embodiments are described in the subject disclosure.

One or more aspects of the subject disclosure include a device, comprising a processing system including a processor, and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations. The operations can comprise determining a first subscription associated with a communication device has expired, the first subscription is for a first group of services for a mobile network. Further operations can comprise receiving, over the mobile network, a first registration request from the communication device, detecting, over the mobile network, a bootstrap profile on the communication device, and providing, over the mobile network, according to the bootstrap profile, limited services to the communication device to subscribe to a second subscription for a second group of services. Additional operations can comprise obtaining subscription information for the second subscription for the second group of services, adjusting, over the mobile network, an operational profile on the communication device according to the subscription information resulting in an adjusted operational profile, and receiving, over the mobile network, a second registration request for the communication device according to the adjusted operation profile. Also, operations can comprise registering the communication device according to the adjusted operational profile, and providing, over the mobile network, the second group of services to the communication device according to the adjusted operational profile.

One or more aspects of the subject disclosure include a machine-readable medium, comprising executable instructions that, when executed by a processing system including a processor, facilitate performance of operations. The operations can comprise determining a first subscription associated with a communication device has expired, the first subscription is for a first group of services for a mobile network. Further operations can comprise converting, over the mobile network via over-the-air (OTA) communications, an operational profile to a bootstrap profile, receiving, over the mobile network, a first registration request from the communication device, detecting, over the mobile network, the bootstrap profile on the communication device, and providing, over the mobile network, according to the bootstrap profile, limited services to the communication device to subscribe to a second subscription for a second group of services. Additional operations can comprise obtaining subscription information for the second subscription for the second group of services, adjusting, over the mobile network, the bootstrap profile to the operational profile on the communication device according to the subscription information resulting in an adjusted operational profile, and receiving, over the mobile network, a second registration request for the communication device according to the adjusted operation profile. Also, operations can comprise registering the communication device according to the adjusted operational profile, and providing, over the mobile network, the second group of services to the communication device according to the adjusted operational profile.

One or more aspects of the subject disclosure include a method. The method can comprise determining, by a processing system including a processor, a first subscription associated with a communication device has expired, the first subscription is for a first group of services for a mobile network. Further, the method can comprise sending, by the processing system, a first notification to a network device that indicates that an operational profile associated with the communication device is inactive, receiving, by the processing system, over the mobile network, a first registration request from the communication device, detecting, by the processing system, over the mobile network, a bootstrap profile on the communication device, and providing, by the processing system, over the mobile network, according to the bootstrap profile, limited services to the communication device to subscribe to a second subscription for a second group of services. In addition, the method can comprise obtaining, by the processing system, subscription information for the second subscription for the second group of services, adjusting, by the processing system, over the mobile network, the operational profile on the communication device according to the subscription information resulting in an adjusted operational profile, and receiving, by the processing system, over the mobile network, a second registration request for the communication device according to the adjusted operation profile. Also, the method can comprise registering, by the processing system, the communication device according to the adjusted operational profile, and providing, by the processing system, over the mobile network, the second group of services to the communication device according to the adjusted operational profile.

Referring now to FIG. 1, a block diagram is shown illustrating an example, non-limiting embodiment of a communications network 100 in accordance with various aspects described herein. For example, communications network 100 can facilitate in whole or in part a communication device with an expired subscription for services to renew the subscription for services, subscribe to different services, or migrate to a different mobile network to subscribe for services. In particular, a communications network 125 is presented for providing broadband access 110 to a plurality of data terminals 114 via access terminal 112, wireless access 120 to a plurality of mobile devices 124 and vehicle 126 via base station or access point 122, voice access 130 to a plurality of telephony devices 134, via switching device 132 and/or media access 140 to a plurality of audio/video display devices 144 via media terminal 142. In addition, communication network 125 is coupled to one or more content sources 175 of audio, video, graphics, text and/or other media. While broadband access 110, wireless access 120, voice access 130 and media access 140 are shown separately, one or more of these forms of access can be combined to provide multiple access services to a single client device (e.g., mobile devices 124 can receive media content via media terminal 142, data terminal 114 can be provided voice access via switching device 132, and so on).

The communications network 125 includes a plurality of network elements (NE) 150, 152, 154, 156, etc. for facilitating the broadband access 110, wireless access 120, voice access 130, media access 140 and/or the distribution of content from content sources 175. The communications network 125 can include a circuit switched or packet switched network, a voice over Internet protocol (VoIP) network, Internet protocol (IP) network, a cable network, a passive or active optical network, a 4G, 5G, or higher generation wireless access network, WIMAX network, UltraWideband network, personal area network or other wireless access network, a broadcast satellite network and/or other communications network.

In various embodiments, the access terminal 112 can include a digital subscriber line access multiplexer (DSLAM), cable modem termination system (CMTS), optical line terminal (OLT) and/or other access terminal. The data terminals 114 can include personal computers, laptop computers, netbook computers, tablets or other computing devices along with digital subscriber line (DSL) modems, data over coax service interface specification (DOCSIS) modems or other cable modems, a wireless modem such as a 4G, 5G, or higher generation modem, an optical modem and/or other access devices.

In various embodiments, the base station or access point 122 can include a 4G, 5G, or higher generation base station, an access point that operates via an 802.11 standard such as 802.11n, 802.11ac or other wireless access terminal. The mobile devices 124 can include mobile phones, e-readers, tablets, phablets, wireless modems, and/or other mobile computing devices.

In various embodiments, the switching device 132 can include a private branch exchange or central office switch, a media services gateway, VoIP gateway or other gateway device and/or other switching device. The telephony devices 134 can include traditional telephones (with or without a terminal adapter), VoIP telephones and/or other telephony devices.

In various embodiments, the media terminal 142 can include a cable head-end or other TV head-end, a satellite receiver, gateway or other media terminal 142. The display devices 144 can include televisions with or without a set top box, personal computers and/or other display devices.

In various embodiments, the content sources 175 include broadcast television and radio sources, video on demand platforms and streaming video and audio services platforms, one or more content data networks, data servers, web servers and other content servers, and/or other sources of media.

In various embodiments, the communications network 125 can include wired, optical and/or wireless links and the network elements 150, 152, 154, 156, etc. can include service switching points, signal transfer points, service control points, network gateways, media distribution hubs, servers, firewalls, routers, edge devices, switches and other network nodes for routing and controlling communications traffic over wired, optical and wireless links as part of the Internet and other public networks as well as one or more private networks, for managing subscriber access, for billing and network management and for supporting other network functions.

FIGS. 2A-2D are block diagrams illustrating example, non-limiting embodiments of systems functioning within the communication network of FIG. 1 in accordance with various aspects described herein. Referring to FIG. 2A, in one or more embodiments, system 200 a can comprise a first network node 202 a communicatively coupled to a first base station 206 a over a communication network 204 a. The communication network 204 a can be a wired communication network, wireless communication networks, or a combination thereof. Further, the system 200 a can comprise the first base station 206 a being communicatively coupled, over a wireless communication network 208 a (e.g. cellular network), to several communication devices 212, 214, 216 including a mobile device 212 associated with a user 210, sensors 214, and smart power meters 216 that can be associated with an entity (e.g. company, enterprise, etc.). The mobile device can comprise a mobile phone, smartphone, laptop computer, tablet computer, smart watch, wearable device, or some other mobile computing device. The sensors and smart power meters can be IoT devices that are owned or operated by a company or some other entity to gather data to process. Further, the communication devices 212, 214, 216 can also include IoT devices, including smart appliances, smart light bulbs, smart sprinklers, smart thermostats, vehicle communication systems, etc. The communication devices 212, 214, 216 may each have a respective expired subscription for services and the user/owner/operator of the communication devices 212, 214, 216 can renew each respective subscription for services, subscribe to different services, or migrate to a different mobile network to subscribe for services, as described herein.

In addition, the first network node 202 a and first base station 206 a and parts of communication network 204 a can be part of a first mobile network operated by a first mobile network operator. In one or more embodiments, each user/owner/operator 210 of communication devices 212, 214, 216 may have entered into a subscription for services that include location services, voice, video, messaging, and communication services, and/or data communication services. At some point in time, the subscription of services may have expired. Previous to the expiration of the subscription for services, any of the communication devices 212, 214, 216 may be provisioned with an operational profile 218 a, 220 a, 222 a by the first mobile network operator. An operational profile can comprise information that includes a combination of mobile network operator data, credentials, and applications provisioned to an embedded universal integrated circuit card or any component performing the function of an embedded universal integrated circuit card (eUICC) of any of the communication devices 212, 214, 216. Further, the eUICC can be an embedded, non-removable card inside any of the communication devices 212, 214, 216 in which the operational profile can be installed. When the subscription for services expires, the first mobile network operator, via over-the-air (OTA) communications, can trigger a fallback attribute on any of the communication devices 212, 214, 216 to convert the operational profile 218 a, 220 a, 222 a to a bootstrap (or provisioning) profile. A bootstrap (or provisioning) profile can comprise information that includes a combination of mobile network operator data, credentials and applications provisioned to an eUICC of any of the communication devices 212, 214, 216 for providing network services by the first mobile network operator solely for the purpose of obtaining/downloading/converting to an operational profile, which the operational profile can then allow any of the communication devices 212, 214, 216 to register for (different) subscription services (or renewed subscription services).

In one or more embodiments, the user/owner/operator 210 of communication devices 212, 214, 216 may renew the subscription for services, if the services according to the previous subscription are no longer available, or if the needs of any one of the communication devices 212, 214, 216 change, the user/owner/operator 210 of may select different services for a new subscription. The renewal of the same services or subscription of different services can be done over a wireless communication network 208 a (e.g. cellular network) when a WiFi network or a wired connection (e.g. USB connection to a laptop computer) is unavailable.

In one or more embodiments, the network node 202 a can detect, over a cellular network, the bootstrap profile 218 b, 220 b, 222 b (in which, in some embodiments, the bootstrap profile was converted from an operational profile) on any one of the communication devices 212, 214, 216. In further embodiments, the network node 202 a can provide, over the cellular network, limited services to any one of the communication devices 212, 214, 216. The limited services allows the user/owner/operator 210 of the communication devices 212, 214, 216 to renew or newly subscribe for a second subscription for a second group of services. The renewal or new subscription may involve one or more other network devices (including the communication devices 212, 214, 216). Further, the network node 202 a can obtain subscription information for a second subscription for a second group of services from one or more of these other network devices.

In additional embodiments, the providing of the limited services to the communication device can comprise providing, over the cellular network, a list of services to any one of the communication devices 212, 214, 216 that includes the second group of services. Further, the obtaining of subscription information can comprise receiving, over the cellular network, a selection of the second group of services from any one of the communication devices 212, 214, 216. The providing of the list of services to some of the communication devices 212, 214, 216 such as mobile device 212 can be through a mobile application on the mobile device 212, through a text message, or presented at a user interface of the particular device (e.g. graphical user interface of a smart refrigerator). The receiving of the selection of the second group of services can be from the mobile application or through a text message.

In further embodiments, renewal of a subscription can be for a sensor but the entity (user or enterprise) associated with the sensor can provide input to renew an expired subscription through a mobile phone of the user (through a mobile application or text message) or an administrative web interface in the case of an enterprise. The network device 202 a can provide a message (through text messaging application or another mobile application) and provide access to a website by providing a link to the website in the message. Referring to FIG. 2D, in other embodiments, the providing of the limited services to the communication devices 212, 214, 216 can comprise providing access to a website hosted on a web server 232 that presents a list of services 234 for the any of the communication devices 212, 214, 216 that includes the second group of services. In addition, the obtaining of subscription information can comprise receiving a selection of the second group of services from the web server 232 (i.e. another network device) by user 210.

Referring back to FIG. 2A, in one or more embodiments, the providing of the limited services can indicate to the first network node 202 a and other network devices on the first mobile network to allow any one of the communication devices 212, 214, 216 to contact a first mobile network operator personnel through customer care system such as, but not limited to, a calling a customer care representative, texting a customer care representative, instant messaging through a chat session with a customer care representative, and/or video conferencing with a customer care representative. The user/owner/operator 210 of communication devices 212, 214, 216 can then indicate to the customer care representative their selection of location, voice, video, messaging, and/or data communication services as part the second group of services to be provided to any one of the communication devices 212, 214, 216. The network node 202 a can receive the selection from a network device associated with the customer care representative as part of the obtaining of subscription information for the second group of services.

In one or more embodiments, a network device that includes a profile management system 226 a can manage whether a communication device 212, 214, 216 has an active operational profile or an inactive operational profile due to an expired subscription for services. Such embodiments can include a network device 202 a receiving a message from another (e.g. billing, administrative, etc.) network device that that the subscription for services for any one of the communication devices 212, 214, 216 has expired. The profile management system 226 a for the mobile network can maintain or manage a list of IMSIs 227A associated with communication devices 212, 214, 216 with expired subscriptions. That is, once the network node 202 a determines one of the communication devices 212, 214, 216 has an expired subscription, it can notify the profile management system to list the IMSI for such a communication device 212, 214, 216 on the IMSI list 227 a for communication devices with expired subscription. In some embodiments, such a notification can include the IMSI of the communication device 212, 214, 216. In other embodiments, the network node 202 a can send a notification to the profile management system 226 a that a communication device 212, 214, 216, has an inactive operational profile. The notification can include identification information such as an IMSI for the operational profile. In such embodiments, the profile management system 226 a can obtain the IMSI for the communication device 212, 214, 216 from another network device according to the operational profile. Subsequently, if any of these communication devices 212, 214, 216 attempt to register with the first mobile network, the profile management system 226 a checks the IMSI list 227 a, and if the IMSI associated with the communication device 212, 214, 216 is listed therein, treats the operational profile with which the communication device 212, 214, 216 attempts to register as a bootstrap profile. Thus, the network device 202 a provides limited services, described herein, to allow the user/operator/owner 210 of the communication device 212, 214, 216 to only renew its subscription or subscribe for a new subscription.

Referring to FIG. 2B, in one or more embodiments, any of the communication devices 212, 214, 216 are provisioned with two profiles, an operational profile 218 a, 220 a, 222 a, and a bootstrap profile 218 b, 220 b, 222 b. In further embodiments, the operational profiles 218 a, 220 a, 222 a can include a Fallback Attribute, that when triggered, makes an operational profile inactive. In additional embodiments, when any of the communication devices 212, 214, 216 attempts to register with the first mobile network after its subscription for services has expired, the communication device 212, 214, 216 would use the bootstrap profile 218 b, 220 b, 222 b to register with the first mobile network. The network device 202 a, upon detecting the bootstrap profile 218 b, 220 b, 222 b, provides limited services, as described herein, to the communication device 212, 214, 216 for the purpose of renewing the subscription for a first group of services or subscribing to a new subscription for a second group of services.

In one or more embodiments, once a user/owner/operator 210 of the communication devices 212, 214, 216 renews or subscribes to a subscription using the limited services, the network device 202 a can adjust the operational profile 218 a, 220 a, 222 a, via OTA communications, on a communication device 212, 214, 216. The adjusting of the operational profile 218 a, 220 a, 222 a can be according to the renewed subscription or a new subscription. That is, the adjusting of the operational profile can comprise providing the OTA communications that include instructions to trigger the Fallback Attribute to make the operational profile active. In other embodiments, the adjusting of the operational profile can include the network device 202 a provisioning, through OTA communications, a different operational profile 218 a, 220 a, 222 a, to the communication devices 212, 214, 216 according to it renewing its subscription or subscribing to different services. In additional embodiments, any one of the operational profiles 218 a, 220 a, 222 a, or bootstrap profiles 218 b, 220 b, 222 b, can be called an eSIM. That is, eSIM can be a term that applies to an operational profile or a bootstrap profile, accordingly.

In one or more embodiments, the user/owner/operator 210 of communication device 212, 214, 216 may not renew an expired subscription but select a different subscription with a second group of services. In such embodiments, communication device 212, 214, 216 can use the same operational profile 218 a, 220 a, 222 a to register with the mobile network to access the newly subscribed second group of services. That is, upon selecting the different subscription for the second group of services, the network node 202 a tracks that this different subscription for the second group of services is associated with the operational 218 a, 220 a, 222 a profile already provisioned on the communication device 212, 214, 216. When registering the communication device 212, 214, 216 with operational profile 218 a, 220 a, 222 a, the network node 202 a can provide the second group of services, accordingly.

In one or more embodiments, the network node 202 a can obtain an IMSI for any one of the communication devices 212, 214, 216 from a corresponding bootstrap profile 218 b, 220 b, 222 b. The obtained IMSI can be provided to the profile management system 226 a. The profile management system 226 a can identify that the IMSI is on the IMSI list 227 a to determine that the communication device 212, 214, 216 be provided limited services to renew its subscription or newly subscribe to different services.

Referring to FIG. 2C, in one or more embodiments, at some point in time, the contractual relationship between the user and the first mobile network operator, and between the entities that own or operate any one of the communication devices 212, 214, 216, and the first mobile network operator may have been terminated or the subscription for the first group or services may have expired. Consequently, a user/owner/operator 210 communication devices 212, 214, 216 can migrate, contract, or subscribe with a second mobile network operator to provide location, voice, video, messaging and/or data communication services for any one of the communication devices 212, 214, 216.

In one or more embodiments, the system 200 c can comprise a second network node 202 b communicatively coupled to a second base station 206 b over a communication network 204 b. The communication network 204 b can be a wired communication network, wireless communication networks, or a combination thereof. Further, the system 200 b can comprise the second base station 206 b being communicatively coupled, over a wireless communication network 208 b (e.g. cellular network), to several communication devices 212, 214, 216 including the mobile device associated with user 210, the sensors, and the smart power meters. In addition, the second network node 202 b and second base station 206 b and parts of communication network 204 b can be part of a second mobile network operated by a second mobile network operator. User/owner/operator 210 of communication device 212, 214, 216 may have contracted (e.g. entered into a subscription) with the second mobile network operator to provide location, voice, video, messaging, and/or data communication services for the communication devices 212, 214, 216, after expiration of the subscription of a first group of service with the first mobile network operator as part of migrating from the first mobile network to the second mobile network. A user can include an entity that could include an enterprise.

In one or more embodiments, communication devices 212, 214, 216 may have been provisioned with a bootstrap profile 218 b, 220 b, 222 b to register for limited services with second mobile network operator in the second mobile network prior to expiration of the subscription with the first mobile network operator. The bootstrap profile 218 b, 220 b, 222 b can be provisioned on the subscriber identification module (SIM), eSIM, or removable SIM associated with any of the communication devices 212, 214, 216. In some embodiments, there can be a roaming agreement between the first mobile network operator and the second mobile network operator to allow for limited services to be provided to any one of the communication devices 212, 214, 216 by the second mobile network operator.

In one or more embodiments, the second network node 202 b can detect a bootstrap profile 218 b, 220 b, 222 b, over the cellular network, on one or more communication devices 212, 214, 216. The detection of the bootstrap profile can be done when a WiFi network or wired connection (e.g. through a USB connection on a laptop computer) is unavailable to the communication devices. In addition, the second network node 202 b can provide the limited services to the one or more communication devices 212, 214, 216. These limited services can include limited connectivity to the second mobile network, as described herein.

In one or more embodiments, the communication devices 212, 214, 216 can subscribe to subscription services such as location, voice, video, messaging, and/or data communication services using the limited services. The network device 202 b can then provision, using OTA communications, an operational profile 218 a, 220 a, 222 a to the communication device 212, 214, 216 so that it can register with the second mobile network and receive the newly subscribed subscription services. That is, the second network node 202 b can detect the operational profile 218 a, 220 a, 222 a on communication device 212, 214, 216 and provide a second group of services for the new subscription of services according to the operational profile.

FIGS. 2E-2F depict illustrative embodiments of methods in accordance with various aspects described herein. Aspects of the methods can be implemented by one or more network nodes and/or a communication device that can include any one of mobile device, sensors, and smart power meters, as described in FIGS. 2A-2D. Referring to FIG. 2E, in one or more embodiments, a communication device can be provisioned with an operational profile and a bootstrap profile. The method 240 can include the network node, at 241, determining a first subscription associated with a communication device has expired. The first subscription is for a first group of services for a mobile network. Further, the method 240 can include the network node, at 242, providing instructions, over the mobile network via over-the-air (OTA) communications, to the communication device to trigger a fallback attribute. The triggering of the fallback attribute causes the operational profile to be inactive by the communication device.

In one or more embodiments, some time later, the user/owner/operator of the communication device decides to renew or newly subscribe for a second group of services with the mobile network operator from the mobile network. Consequently, method 240 can include the network node, at 244, receiving, over the mobile network, a first registration request from the communication device. That is, the communication device is attempting to register with the bootstrap profile. In addition, method 240 can include the network node, at 245, detecting, over the mobile network, the bootstrap profile on the communication device. Also, method 240 can include the network node, at 246, providing, over the mobile network, according to the bootstrap profile, limited services to the communication device to subscribe to a second subscription for a second group of services, as described herein. Note, in some embodiments, the first group of services and the second group of services may be the same. The method 240 can include the network node, at 247, facilitating, enabling or allowing the communication device renewing or newly subscribing for the second subscription for a second group of services. Further, the method 240 can include the network node, at 248, obtaining subscription information for the second subscription for the second group of services from a network device. For example, the user/owner/operator of the communication device may be provided limited services to navigate to the mobile network operator website and select to renew or newly subscribe for a second subscription of services. The web server hosted the website may receive the selection and forward the subscription information for the second subscription to the network node, accordingly.

In one or more embodiments, the method 240 can include the network node, at 249, adjusting, over the mobile network, an operational profile on the communication device according to the subscription information resulting in an adjusted operational profile. In some embodiments, the network node, through OTA communications, adjusts the operational profile to make it active. In other embodiments, the adjusting of the operational profile comprises providing, over the mobile network via OTA communications, instructions to the communication device to trigger the fallback attribute. The triggering of the fallback attribute causes the operational profile to be active. Having an active operational profile allows the communication device to register with the mobile network so that it can receive the second group of services of the second subscription. Thus, the method 240 can include the network node, at 250, receiving, over the mobile network, a second registration request for the communication device according to the adjusted operation profile. Further, the method 240 can include the network node, at 251, registering the communication device according to the adjusted operational profile. In addition, the method 240 can include the network node, at 252, providing, over the mobile network, the second group of services to the communication device according to the adjusted operational profile.

Referring to FIG. 2F, in one or more embodiments, a communication device can be provisioned with an operational profile that can be converted into a bootstrap profile upon triggering its fallback attribute. Further, the resulting bootstrap profile can be converted back to the operational profile by triggering the fallback attribute again. The method 253 can include the network node, at 254, determining a first subscription associated with a communication device has expired. The first subscription is for a first group of services for a mobile network. Further, the method 253 can include the network node, at 255, providing instructions, over the mobile network via over-the-air (OTA) communications, to the communication device to trigger a fallback attribute. The triggering of the fallback attribute causes the operational profile to be inactive. In addition, the method 253 can include that triggering of the fallback attribute causes, at 256, the communication device to convert the operational profile into the bootstrap profile.

In one or more embodiments, some time later, the user/owner/operator of the communication device decides to renew or newly subscribe for a second group of services (second subscription) with the mobile network operator from the mobile network. Consequently, method 253 can include the network node, at 258, receiving, over the mobile network, a first registration request from the communication device. That is, the communication device is attempting to register with the bootstrap profile. In addition, method 253 can include the network node, at 259, detecting, over the mobile network, the bootstrap profile on the communication device. Also, method 253 can include the network node, at 260, providing, over the mobile network, according to the bootstrap profile, limited services to the communication device to subscribe to a second subscription for a second group of services, as described herein. Note, in some embodiments, the first group of services and the second group of services may be the same. The method 240 can include the network node, at 261, facilitating, enabling or allowing the communication device renewing or newly subscribing for the second subscription for a second group of services. Further, the method 253 can include the network node, at 262, obtaining subscription information for the second subscription for the second group of services from a network device. For example, the user/owner/operator of the communication device may be provided limited services to navigate to the mobile network operator website and select to renew or newly subscribe for a second subscription of services. The web server hosted the website may receive the selection and forward the subscription information for the second subscription to the network node, accordingly.

In one or more embodiments, the method 253 can include the network node, at 263, adjusting, over the mobile network, the bootstrap profile on the communication device according to the subscription information. In some embodiments, the network node, through OTA communications, adjusts the bootstrap profile by providing instructions to the communication device to trigger the fallback attribute. The method 253 can include, at 264, the triggering of the fallback attribute causing the communication device to convert the bootstrap profile into the operational profile, which is now active. Having an active operational profile allows the communication device to register with the mobile network so that it can receive the second group of services of the second subscription. Thus, the method 253 can include the network node, at 265, receiving, over the mobile network, a second registration request for the communication device according to the operation profile. Further, the method 253 can include the network node, at 266, registering the communication device according to the operational profile. In addition, the method 253 can include the network node, at 267, providing, over the mobile network, the second group of services to the communication device according to the operational profile.

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIGS. 2E-2F, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

Portions of embodiments described herein can be combined with other portions of embodiments.

Referring now to FIG. 2G, a block diagram illustrating an example, non-limiting embodiment of a system is shown. As seen in this FIG., mobile communication device 2102 (e.g., a smartphone) can be configured for (and/or engage in) operative bi-directional communication with server 2106 (server 2106 can be, for example, part of a communications network operated by a network provider). In one example, the bi-directional communication between the mobile communication device 2102 and the server 2106 can be via a wired communication path, a wireless communication path, or any combination thereof. In one example, the bi-directional communication between the mobile communication device 2102 and the server 2106 can be via the Internet.

Still referring to FIG. 2G, mobile communication device 2102 can be configured for (and/or engage in) operative bi-directional communication with each of devices 2104A, 2104B, 2104C. In one example, the bi-directional communication between the mobile communication device 2102 and each of devices 2104A, 2104B, 2104C can be via a wired communication path, a wireless communication path, or any combination thereof. In one example, the bi-directional communication between the mobile communication device 2102 and each of devices 2104A, 2104B, 2104C can be via the Internet. In one example, the bi-directional communication between the mobile communication device 2102 and each of devices 2104A, 2104B, 2104C can be via a wireless near field communication path. In various examples, each of devices 2104A, 2104B, 2104C can be an IoT device, a mobile communication device (e.g., a mobile telephone, a tablet, a netbook computer, a notebook computer), a computing device, or any combination thereof.

Still referring to FIG. 2G, each of devices 2104A, 2104B, 2104C can be configured for (and/or engage in) operative bi-directional communication with server 2106. In one example, the bi-directional communication between each of devices 2104A, 2104B, 2104C and the server 2106 can be via a wired communication path, a wireless communication path, or any combination thereof.

Still referring to FIG. 2G, device 2104A can be configured for (and/or engage in) operative bi-directional communication with each of devices 2104D and 2104F. In one example, the bi-directional communication between device 2104A and each of devices 2104D and 2104F can be via a wired communication path, a wireless communication path, or any combination thereof. In one example, the bi-directional communication between device 2104A and each of devices 2104D and 2104F can be via a wireless near field communication path. In various examples, each of devices 2104D and 2104F can be an IoT device, a mobile communication device (e.g., a mobile telephone, a tablet, a netbook computer, a notebook computer), a computing device, or any combination thereof.

Still referring to FIG. 2G, device 2104D can be configured for (and/or engage in) operative bi-directional communication device 2104E. In one example, the bi-directional communication between device 2104D and device 2104E can be via a wired communication path, a wireless communication path, or any combination thereof. In one example, the bi-directional communication between device 2104D and device 2104E can be via a near field communication path. In various examples, device 2104E can be an IoT device, a mobile communication device (e.g., a mobile telephone, a tablet, a netbook computer, a notebook computer), a computing device, or any combination thereof.

Still referring to FIG. 2G, each of devices 2104D, 2104E, 2104F can be configured for (and/or engage in) operative bi-directional communication with server 2106. In one example, the bi-directional communication between each of devices 2104D, 2104E, 2104F and the server 2106 can be via a wired communication path, a wireless communication path, or any combination thereof.

In various embodiments, the bi-directional communication capability described in connection with this FIG. 2G can be used for facilitate sharing of operational profiles between/among devices, as described herein.

Referring now to FIG. 2H, various steps of a method 2200 according to an embodiment are shown. As seen in this FIG. 2H, step 2202 comprises identifying (e.g., by a mobile communication device) a plurality of operational profiles that are to be shared by a plurality of devices. Next, step 2204 comprises assigning (e.g., by the mobile communication device) a first operational profile of the plurality of operational profiles to a first device of the plurality of devices. Next, step 2206 comprises assigning (e.g., by the mobile communication device) a second operational profile of the plurality of operational profiles to a second device of the plurality of devices. Next, step 2208 comprises facilitating (e.g., by the mobile communication device) provision of the first operational profile on the first device. Next, step 2210 comprises facilitating (e.g., by the mobile communication device) provision of the second operational profile on the second device. In other examples, a server (e.g., associated with a communication network operated by a network provider) can perform (by itself or in combination with other elements, such as the mobile communication device) the identifying, the assigning of the first operational profile, the assigning of the second operational profile, the provisioning of the first operational profile, and/or the provisioning of the second operational profile. In other examples, one or more IoT devices can each include “intelligence” (such as functionality) to perform one or more functions described herein in order to implement provisioning of a given IoT device with a given operational profile.

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 2H, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

Referring now to FIG. 2I, various steps of a method 2300 according to an embodiment are shown. As seen in this FIG. 2I, step 2302 comprises receiving (e.g., by a mobile communication device), from a server that is part of a communications network operated by a network provider, an identification of a plurality of operational profiles, each operational profile being assigned to a different Internet of Things (IoT) device of a plurality of IoT devices. Next, step 2304 comprises providing (e.g., by the mobile communication device), based upon each operational profile being assigned to a different IoT device, a first operational profile of the plurality of operational profiles to a first IoT device of the plurality of IoT devices. Next, step 2306 comprises providing (e.g., by the mobile communication device), based upon each operational profile being assigned to a different IoT device, a second operational profile of the plurality of operational profiles to a second IoT device of the plurality of IoT devices. In other examples, a server (e.g., associated with a communication network operated by a network provider) can perform (by itself or in combination with other elements, such as the mobile communication device) an identifying of the plurality of operational profiles, an assigning of the first operational profile, an assigning of the second operational profile, the providing of the first operational profile, and/or the providing of the second operational profile. In other examples, one or more IoT devices can each include “intelligence” (such as functionality) to perform one or more functions described herein in order to implement provisioning of a given IoT device with a given operational profile.

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 2I, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

Referring now to FIG. 2J, various steps of a method 2400 according to an embodiment are shown. As seen in this FIG. 2J, step 2402 comprises identifying, by a processing system of a mobile communication device including a processor, a plurality of operational profiles that are to be shared by a plurality of Internet of Things (IoT) devices. Next, step 2404 comprises providing by the processing system, based upon the identifying, a first operational profile of the plurality of operational profiles to a first IoT device of the plurality of IoT devices, the providing of the first operational profile enabling use by the first IoT device of the first operational profile. Next, step 2406 comprises providing by the processing system, based upon the identifying, a second operational profile of the plurality of operational profiles to the first IoT device, the providing of the second operational profile enabling the first IoT device to send to a second IoT device the second operational profile for use by the second IoT device. In other examples, a server (e.g., associated with a communication network operated by a network provider) can perform (by itself or in combination with other elements, such as the mobile communication device) the identifying, the providing of the first operational profile, and/or the providing of the second operational profile. In other examples, one or more IoT devices can each include “intelligence” (such as functionality) to perform one or more functions described herein in order to implement provisioning of a given IoT device with a given operational profile.

While for purposes of simplicity of explanation, the respective processes are shown and described as a series of blocks in FIG. 2J, it is to be understood and appreciated that the claimed subject matter is not limited by the order of the blocks, as some blocks may occur in different orders and/or concurrently with other blocks from what is depicted and described herein. Moreover, not all illustrated blocks may be required to implement the methods described herein.

As described herein, various embodiments provide for managing IoT devices (e.g., electric meters, water meters) through use of blocks of operational profiles.

In one or more embodiments, blocks of operational profiles can be assigned and/or distributed via a UE (user equipment)/phone to associated IoT devices. The UE/phone can have a block of operational profiles to be assigned to various IoT devices. The assignments can be, for example, via OTA based on direction from UE/phone. The OTA communication can be, for example, directly with the IoT device utilizing bootstrap profile of the IoT device and/or can be distributed via the UE/phone through short range communication directly with the IoT(s). In one example, the assignments can be static—once assigned the operational profile stays with that IoT device. In another example, the assignments can be dynamic—a pool of operational profiles that the IOTs can utilize when needing to communicate—coordination can be, for example, by the UE/phone to prevent simultaneous use of a same operational profile by more than one IoT at a same time.

In one or more embodiments, a “master” operational profile can be used which controls/manages “slave” operational profiles (e.g., which operational profile goes in a given car). In one example, a determination can be made (e.g., via checking of a policy) to verify whether a given IoT device is functional to re-use operational profile on another device. In one example, a network and/or an IoT device can have a detection policy to verify whether the IoT device is functional.

In one or more embodiments, a communication device, or “CD” (e.g., phone or other UE) can manage assignment/distribution of a block of reserved operational profiles for one or more IoTs (e.g., a group of IoTs) and/or for one or more other CDs (e.g., a group of CDs).

In one or more embodiments, a CD manages assignment of a group of eSIMs to a group of IoTs and/or CDs. In one example, the IoT/CD obtains eSIM from a group of reserved eSIMs by way of communication with a “master” CD. In another example, a network server provisions a group of eSIMS to a group of IoTs/CDs based on coordination by a “master” CD associated with the group of IoTs/CDs.

In one example, an operational profile can be shared between/among a plurality of IoT devices via “time sharing”. In one example, an operational profile can define a relationship between a provisioned device and a network. In one example, an operational profile can be re-built by a network server. In one example, an operational profile can be shared by different machines (e.g., one operational profile can be shared (at different times) by 20 water/power meters). In one example, a smartphone can act as a master to manage a group of operational profiles (e.g., using a “master/slave” relationship). In one example, a smartphone can act as the “master” and a car (or other vehicle) can receive from the smartphone an operational profile for use by the car (or other vehicle). In another example, one “smart device” (such as in a house) can manage other “dumb” devices in the house. In one example, a “master” operational profile can have a higher level of privileges as compared to a “slave” operational profile. In one example, a “master “operational profile can facilitate enabling/disabling services (e.g., services associated with a “slave” operational profile). In another example, a Bluetooth-enabled device can be given an operational profile by a UE/phone. In one example, a policy can specify whether an operational profile can be changed and/or turned off. In another example, communication (e.g., with one or more IoTs) can be via near field communication. In one example, communication (e.g., with one or more IoTs) can be via far field communication.

In one example, one or more operational profiles can be provisioned on a “swarm” of devices. In one example, one or more operational profiles can be communicated between/among a plurality of IoTs via “mesh networking”. In one example, as operational profiles become enabled, the IoTs can communicate and re-profile one another. In one example, one or more operational profiles can be communicated to a plurality of IoTs via “hub and spoke networking” (e.g., communicated to a plurality of IoTs from a given source (for instance, UE/phone)). In another example, one or more operational profiles can be communicated between/among a plurality of IoTs via a decentralized control mechanism.

In one or more embodiments, various mechanisms can facilitate managing profiles (e.g., bootstrap profile(s) and/or operational profile(s)). In one specific example, a mechanism can facilitate obtaining a new operational profile in an IoT device. In another specific example, a mechanism can facilitate OTA management (e.g., downloading, updating) of one or more bootstrap profiles and/or one or more operational profiles in an IoT device.

In one or more embodiments, mechanisms can be provided to facilitate provisioning an IoT device with an operational profile having “time to live”. In one specific example, after expiration of a time period (and/or based on inability to utilize the operational profile), the IoT device subsequently utilizes its bootstrap profile to obtain a new operational profile.

In one or more embodiments, mechanisms can be provided to facilitate monitoring and/or reassigning an operational profile when an IoT device is no longer communicating. In one specific example, the IoT device performs scheduled registrations that can be monitored and lack of a registration can trigger an operational profile download via a bootstrap profile.

In one or more embodiments, mechanisms can be provided to facilitate OTA provisioning of a new operational profile for an IoT device, wherein the provisioning can he based on monitoring by the IoT device and/or monitoring by the network. In one specific example, the network can monitor for failure to timely register by the IoT device (such failure can then trigger provisioning of, for example, a new operational profile). In another specific example, the IoT device can monitor for a registration failure (such failure can then trigger provisioning of, for example, a new operational profile). In another specific example, the network can monitor for time expiration that is assigned to a particular operational profile (such time expiration can then trigger provisioning of, for example, a new operational profile). In another specific example, the IoT device can monitor for time expiration that is assigned to a particular operational profile (such time expiration can then trigger provisioning of, for example, a new operational profile). In another specific example, the OTA can be performed over any network (e.g., WiFi and/or cellular).

In one or more embodiments, mechanisms can be provided to avoid (or help avoid) a situation in which an IoT device would be unable to connect to a network due to an “old” (or out-of-date) operational profile. In one specific example, a “time to live” value can be assigned to an operational profile, wherein the operational profile (at the expiration of the “time to live”) is then converted to a bootstrap profile (providing limited connectivity/capability). The bootstrap profile can then enable the IoT to connect via, e.g., a cellular network, with a network server for subscription renewal/update/new operational profile. In this example, there would be no need for a separate bootstrap profile associated with the IoT device. In various examples, the conversion can be by the IoT device and/or by the network.

As described herein, in various embodiments, an operational profile can have a limited time of use, wherein OTA communication is utilized to provide a new operational profile. In one specific example, a network server can facilitate for an IoT device an OTA provisioning associated with an eSIM of the IoT device according to expiration of “time of life” for a previous eSIM of the IoT device and/or according to a lack of registration by the IoT device. In another specific example, an IoT device can perform periodic registration and can receive (e.g., via an OTA communication) an eSIM according to expiration of “time of life” for a previous eSIM of the IoT device and/or according to a failure to register by the IoT device.

In one or more embodiments, various devices can benefit from the eSIM management described herein (e.g., remotely manageable eSIM with bootstrap profile and/or operational profile). For example, various embodiments can be implemented in the context of wearable electronics. In one specific example, a shirt can monitor a wearer's heartbeat and can summon, e.g., a drone, if a particular event happens (e.g., heart attack, sickness). In another specific example, an automated methodology can manage the eSIM in, for instance, a circumstance wherein it would be difficult for a user to manage this. In another specific example, an automated methodology can manage the eSIM in, for instance, a circumstance wherein one would not want to rely on WiFi alone. In another specific example, the device can have a power source and/or be waterproof. In another specific example, the device can track when the user wears a particular item of clothing and under what conditions (the tracked information regarding each item of clothing can be, for example, stored securely in the eSIM). In another specific example, a “skinny eSIM” can be utilized that would take less storage space than a “regular eSIM”.

In one or more embodiments, mechanisms can be provided to facilitate virtual shopping for clothes. In one specific example, a device can have a camera and software capable of measuring the user. These measurements could then create a virtual form of the user which could then be used to try on virtual clothes. Measurements could be stored on the eSIM (e.g., in a circumstance wherein it is desirable and/or required for the measurements to be protected). In another specific example, such storage on/protection by the eSIM can be applied to devices in general that have recording capabilities (e.g., the recordings could be stored in the eSIM and accessed using one or more conventional techniques that facilitates SIM security). In another specific example, the device could be incorporated into user's eye glasses.

In one or more embodiments, mechanisms can be provided to facilitate use/operation of one or more driverless cars. In one specific example, an eSIM can be shared between a user's personal device and a driverless car that the user has summoned. In another specific example, a user can have a “driverless car profile” that is downloaded to any driverless vehicle that the user is in.

In one or more embodiments, mechanisms can be provided to facilitate use/operation of one or more cameras (“movies everywhere”). In one specific example, an eSIM can be used to facilitate managing storage of recordings and keeping communication services up-to-date.

In various examples, a block of operational profiles can be used by any desired type(s) of devices. In various specific examples, the devices can comprise communication devices (each of which can be associated with a respective user). In various examples, a communication device can be a smartphone, a tablet, a notebook computer, a netbook computer, a mobile phone.

In various examples, the operational profiles can be used by a group of communication devices associated with (such as owned/leased by) a given user and/or associated with (such as being located at) a given premises and/or associated with (such as owned/leased by) a given entity. In various examples, the operational profiles can be used by one or more tablets, one or more laptops, one or more intelligent TVs, one or more smart lightbulbs, one or more sensors, or any combination thereof.

In one example, an IoT device does not have a user interface (“UI”). In another example, an IoT device does have a user interface (“UI”). In one example, an IoT device has limited communication functions (e.g., relative to one or more other devices). In one example, an IoT device does not have limited communication functions (e.g., relative to one or more other devices). In another example, an IoT device is a communication device that includes certain capabilities (e.g., sensor capabilities). In another example, an IoT device is a communication device that lacks certain capabilities (e.g., a user interface).

Referring now to FIG. 3, a block diagram 300 is shown illustrating an example, non-limiting embodiment of a virtualized communication network in accordance with various aspects described herein. In particular a virtualized communication network is presented that can be used to implement some or all of the subsystems and functions of communication network 100, the subsystems and functions of system 200 a, 200 b, 200 c, 230 and methods 240, 253 presented in FIGS. 1, 2A-2F and 3. For example, virtualized communication network 300 can facilitate in whole or in part a communication device with an expired subscription for services to renew the subscription for services, subscribe to different services, or migrate to a different mobile network to subscribe for services.

In particular, a cloud networking architecture is shown that leverages cloud technologies and supports rapid innovation and scalability via a transport layer 350, a virtualized network function cloud 325 and/or one or more cloud computing environments 375. In various embodiments, this cloud networking architecture is an open architecture that leverages application programming interfaces (APIs); reduces complexity from services and operations; supports more nimble business models; and rapidly and seamlessly scales to meet evolving customer requirements including traffic growth, diversity of traffic types, and diversity of performance and reliability expectations.

In contrast to traditional network elements—which are typically integrated to perform a single function, the virtualized communication network employs virtual network elements (VNEs) 330, 332, 334, etc. that perform some or all of the functions of network elements 150, 152, 154, 156, etc. For example, the network architecture can provide a substrate of networking capability, often called Network Function Virtualization Infrastructure (NFVI) or simply infrastructure that is capable of being directed with software and Software Defined Networking (SDN) protocols to perform a broad variety of network functions and services. This infrastructure can include several types of substrates. The most typical type of substrate being servers that support Network Function Virtualization (NFV), followed by packet forwarding capabilities based on generic computing resources, with specialized network technologies brought to bear when general purpose processors or general purpose integrated circuit devices offered by merchants (referred to herein as merchant silicon) are not appropriate. In this case, communication services can be implemented as cloud-centric workloads.

As an example, a traditional network element 150 (shown in FIG. 1), such as an edge router can be implemented via a VNE 330 composed of NFV software modules, merchant silicon, and associated controllers. The software can be written so that increasing workload consumes incremental resources from a common resource pool, and moreover so that it's elastic: so the resources are only consumed when needed. In a similar fashion, other network elements such as other routers, switches, edge caches, and middle-boxes are instantiated from the common resource pool. Such sharing of infrastructure across a broad set of uses makes planning and growing infrastructure easier to manage.

In an embodiment, the transport layer 350 includes fiber, cable, wired and/or wireless transport elements, network elements and interfaces to provide broadband access 110, wireless access 120, voice access 130, media access 140 and/or access to content sources 175 for distribution of content to any or all of the access technologies. In particular, in some cases a network element needs to be positioned at a specific place, and this allows for less sharing of common infrastructure. Other times, the network elements have specific physical layer adapters that cannot be abstracted or virtualized, and might require special DSP code and analog front-ends (AFEs) that do not lend themselves to implementation as VNEs 330, 332 or 334. These network elements can be included in transport layer 350.

The virtualized network function cloud 325 interfaces with the transport layer 350 to provide the VNEs 330, 332, 334, etc. to provide specific NFVs. In particular, the virtualized network function cloud 325 leverages cloud operations, applications, and architectures to support networking workloads. The virtualized network elements 330, 332 and 334 can employ network function software that provides either a one-for-one mapping of traditional network element function or alternately some combination of network functions designed for cloud computing. For example, VNEs 330, 332 and 334 can include route reflectors, domain name system (DNS) servers, and dynamic host configuration protocol (DHCP) servers, system architecture evolution (SAE) and/or mobility management entity (MME) gateways, broadband network gateways, IP edge routers for IP-VPN, Ethernet and other services, load balancers, distributers and other network elements. Because these elements don't typically need to forward large amounts of traffic, their workload can be distributed across a number of servers—each of which adds a portion of the capability, and overall which creates an elastic function with higher availability than its former monolithic version. These virtual network elements 330, 332, 334, etc. can be instantiated and managed using an orchestration approach similar to those used in cloud compute services.

The cloud computing environments 375 can interface with the virtualized network function cloud 325 via APIs that expose functional capabilities of the VNEs 330, 332, 334, etc. to provide the flexible and expanded capabilities to the virtualized network function cloud 325. In particular, network workloads may have applications distributed across the virtualized network function cloud 325 and cloud computing environment 375 and in the commercial cloud, or might simply orchestrate workloads supported entirely in NFV infrastructure from these third party locations.

Turning now to FIG. 4, there is illustrated a block diagram of a computing environment in accordance with various aspects described herein. In order to provide additional context for various embodiments of the embodiments described herein, FIG. 4 and the following discussion are intended to provide a brief, general description of a suitable computing environment 400 in which the various embodiments of the subject disclosure can be implemented. In particular, computing environment 400 can be used in the implementation of network elements 150, 152, 154, 156, access terminal 112, base station or access point 122, switching device 132, media terminal 142, and/or VNEs 330, 332, 334, etc. Each of these devices can be implemented via computer-executable instructions that can run on one or more computers, and/or in combination with other program modules and/or as a combination of hardware and software. For example, computing environment 400 can facilitate in whole or in part a communication device with an expired subscription for services to renew the subscription for services, subscribe to different services, or migrate to a different mobile network to subscribe for services. Further, the network devices, network nodes, communication devices, mobile devices, sensors, smart power meters, IoT devices, and web server can comprise the computing environment 400.

Generally, program modules comprise routines, programs, components, data structures, etc., that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the methods can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, minicomputers, mainframe computers, as well as personal computers, hand-held computing devices, microprocessor-based or programmable consumer electronics, and the like, each of which can be operatively coupled to one or more associated devices.

As used herein, a processing circuit includes one or more processors as well as other application specific circuits such as an application specific integrated circuit, digital logic circuit, state machine, programmable gate array or other circuit that processes input signals or data and that produces output signals or data in response thereto. It should be noted that while any functions and features described herein in association with the operation of a processor could likewise be performed by a processing circuit.

The illustrated embodiments of the embodiments herein can be also practiced in distributed computing environments where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

Computing devices typically comprise a variety of media, which can comprise computer-readable storage media and/or communications media, which two terms are used herein differently from one another as follows. Computer-readable storage media can be any available storage media that can be accessed by the computer and comprises both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer-readable storage media can be implemented in connection with any method or technology for storage of information such as computer-readable instructions, program modules, structured data or unstructured data.

Computer-readable storage media can comprise, but are not limited to, random access memory (RAM), read only memory (ROM), electrically erasable programmable read only memory (EEPROM),flash memory or other memory technology, compact disk read only memory (CD-ROM), digital versatile disk (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices or other tangible and/or non-transitory media which can be used to store desired information. In this regard, the terms “tangible” or “non-transitory” herein as applied to storage, memory or computer-readable media, are to be understood to exclude only propagating transitory signals per se as modifiers and do not relinquish rights to all standard storage, memory or computer-readable media that are not only propagating transitory signals per se.

Computer-readable storage media can be accessed by one or more local or remote computing devices, e.g., via access requests, queries or other data retrieval protocols, for a variety of operations with respect to the information stored by the medium.

Communications media typically embody computer-readable instructions, data structures, program modules or other structured or unstructured data in a data signal such as a modulated data signal, e.g., a carrier wave or other transport mechanism, and comprises any information delivery or transport media. The term “modulated data signal” or signals refers to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in one or more signals. By way of example, and not limitation, communication media comprise wired media, such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

With reference again to FIG. 4, the example environment can comprise a computer 402, the computer 402 comprising a processing unit 404, a system memory 406 and a system bus 408. The system bus 408 couples system components including, but not limited to, the system memory 406 to the processing unit 404. The processing unit 404 can be any of various commercially available processors. Dual microprocessors and other multiprocessor architectures can also be employed as the processing unit 404.

The system bus 408 can be any of several types of bus structure that can further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and a local bus using any of a variety of commercially available bus architectures. The system memory 406 comprises ROM 410 and RAM 412. A basic input/output system (BIOS) can be stored in a non-volatile memory such as ROM, erasable programmable read only memory (EPROM), EEPROM, which BIOS contains the basic routines that help to transfer information between elements within the computer 402, such as during startup. The RAM 412 can also comprise a high-speed RAM such as static RAM for caching data.

The computer 402 further comprises an internal hard disk drive (HDD) 414 (e.g., EIDE, SATA), which internal HDD 414 can also be configured for external use in a suitable chassis (not shown), a magnetic floppy disk drive (FDD) 416, (e.g., to read from or write to a removable diskette 418) and an optical disk drive 420, (e.g., reading a CD-ROM disk 422 or, to read from or write to other high capacity optical media such as the DVD). The HDD 414, magnetic FDD 416 and optical disk drive 420 can be connected to the system bus 408 by a hard disk drive interface 424, a magnetic disk drive interface 426 and an optical drive interface 428, respectively. The hard disk drive interface 424 for external drive implementations comprises at least one or both of Universal Serial Bus (USB) and Institute of Electrical and Electronics Engineers (IEEE) 1394 interface technologies. Other external drive connection technologies are within contemplation of the embodiments described herein.

The drives and their associated computer-readable storage media provide nonvolatile storage of data, data structures, computer-executable instructions, and so forth. For the computer 402, the drives and storage media accommodate the storage of any data in a suitable digital format. Although the description of computer-readable storage media above refers to a hard disk drive (HDD), a removable magnetic diskette, and a removable optical media such as a CD or DVD, it should be appreciated by those skilled in the art that other types of storage media which are readable by a computer, such as zip drives, magnetic cassettes, flash memory cards, cartridges, and the like, can also be used in the example operating environment, and further, that any such storage media can contain computer-executable instructions for performing the methods described herein.

A number of program modules can be stored in the drives and RAM 412, comprising an operating system 430, one or more application programs 432, other program modules 434 and program data 436. All or portions of the operating system, applications, modules, and/or data can also be cached in the RAM 412. The systems and methods described herein can be implemented utilizing various commercially available operating systems or combinations of operating systems.

A user can enter commands and information into the computer 402 through one or more wired/wireless input devices, e.g., a keyboard 438 and a pointing device, such as a mouse 440. Other input devices (not shown) can comprise a microphone, an infrared (IR) remote control, a joystick, a game pad, a stylus pen, touch screen or the like. These and other input devices are often connected to the processing unit 404 through an input device interface 442 that can be coupled to the system bus 408, but can be connected by other interfaces, such as a parallel port, an IEEE 1394 serial port, a game port, a universal serial bus (USB) port, an IR interface, etc.

A monitor 444 or other type of display device can be also connected to the system bus 408 via an interface, such as a video adapter 446. It will also be appreciated that in alternative embodiments, a monitor 444 can also be any display device (e.g., another computer having a display, a smart phone, a tablet computer, etc.) for receiving display information associated with computer 402 via any communication means, including via the Internet and cloud-based networks. In addition to the monitor 444, a computer typically comprises other peripheral output devices (not shown), such as speakers, printers, etc.

The computer 402 can operate in a networked environment using logical connections via wired and/or wireless communications to one or more remote computers, such as a remote computer(s) 448. The remote computer(s) 448 can be a workstation, a server computer, a router, a personal computer, portable computer, microprocessor-based entertainment appliance, a peer device or other common network node, and typically comprises many or all of the elements described relative to the computer 402, although, for purposes of brevity, only a remote memory/storage device 450 is illustrated. The logical connections depicted comprise wired/wireless connectivity to a local area network (LAN) 452 and/or larger networks, e.g., a wide area network (WAN) 454. Such LAN and WAN networking environments are commonplace in offices and companies, and facilitate enterprise-wide computer networks, such as intranets, all of which can connect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 402 can be connected to the LAN 452 through a wired and/or wireless communication network interface or adapter 456. The adapter 456 can facilitate wired or wireless communication to the LAN 452, which can also comprise a wireless AP disposed thereon for communicating with the adapter 456.

When used in a WAN networking environment, the computer 402 can comprise a modem 458 or can be connected to a communications server on the WAN 454 or has other means for establishing communications over the WAN 454, such as by way of the Internet. The modem 458, which can be internal or external and a wired or wireless device, can be connected to the system bus 408 via the input device interface 442. In a networked environment, program modules depicted relative to the computer 402 or portions thereof, can be stored in the remote memory/storage device 450. It will be appreciated that the network connections shown are example and other means of establishing a communications link between the computers can be used.

The computer 402 can be operable to communicate with any wireless devices or entities operatively disposed in wireless communication, e.g., a printer, scanner, desktop and/or portable computer, portable data assistant, communications satellite, any piece of equipment or location associated with a wirelessly detectable tag (e.g., a kiosk, news stand, restroom), and telephone. This can comprise Wireless Fidelity (Wi-Fi) and BLUETOOTH® wireless technologies. Thus, the communication can be a predefined structure as with a conventional network or simply an ad hoc communication between at least two devices.

Wi-Fi can allow connection to the Internet from a couch at home, a bed in a hotel room or a conference room at work, without wires. Wi-Fi is a wireless technology similar to that used in a cell phone that enables such devices, e.g., computers, to send and receive data indoors and out; anywhere within the range of a base station. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b, g, n, ac, ag, etc.) to provide secure, reliable, fast wireless connectivity. A Wi-Fi network can be used to connect computers to each other, to the Internet, and to wired networks (which can use IEEE 802.3 or Ethernet). Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands for example or with products that contain both bands (dual band), so the networks can provide real-world performance similar to the basic 10 BaseT wired Ethernet networks used in many offices.

Turning now to FIG. 5, an embodiment 500 of a mobile network platform 510 is shown that is an example of network elements 150, 152, 154, 156, and/or VNEs 330, 332, 334, etc. For example, platform 510 can facilitate in whole or in part a communication device with an expired subscription for services to renew the subscription for services, subscribe to different services, or migrate to a different mobile network to subscribe for services.

In one or more embodiments, the mobile network platform 510 can generate and receive signals transmitted and received by base stations or access points such as base station or access point 122. Generally, mobile network platform 510 can comprise components, e.g., nodes, gateways, interfaces, servers, or disparate platforms, that facilitate both packet-switched (PS) (e.g., internet protocol (IP), frame relay, asynchronous transfer mode (ATM)) and circuit-switched (CS) traffic (e.g., voice and data), as well as control generation for networked wireless telecommunication. As a non-limiting example, mobile network platform 510 can be included in telecommunications carrier networks, and can be considered carrier-side components as discussed elsewhere herein. Mobile network platform 510 comprises CS gateway node(s) 512 which can interface CS traffic received from legacy networks like telephony network(s) 540 (e.g., public switched telephone network (PSTN), or public land mobile network (PLMN)) or a signaling system #7 (SS7) network 560. CS gateway node(s) 512 can authorize and authenticate traffic (e.g., voice) arising from such networks. Additionally, CS gateway node(s) 512 can access mobility, or roaming, data generated through SS7 network 560; for instance, mobility data stored in a visited location register (VLR), which can reside in memory 530. Moreover, CS gateway node(s) 512 interfaces CS-based traffic and signaling and PS gateway node(s) 518. As an example, in a 3GPP UMTS network, CS gateway node(s) 512 can be realized at least in part in gateway GPRS support node(s) (GGSN). It should be appreciated that functionality and specific operation of CS gateway node(s) 512, PS gateway node(s) 518, and serving node(s) 516, is provided and dictated by radio technology(ies) utilized by mobile network platform 510 for telecommunication over a radio access network 520 with other devices, such as a radiotelephone 575.

In addition to receiving and processing CS-switched traffic and signaling, PS gateway node(s) 518 can authorize and authenticate PS-based data sessions with served mobile devices. Data sessions can comprise traffic, or content(s), exchanged with networks external to the mobile network platform 510, like wide area network(s) (WANs) 550, enterprise network(s) 570, and service network(s) 580, which can be embodied in local area network(s) (LANs), can also be interfaced with mobile network platform 510 through PS gateway node(s) 518. It is to be noted that WANs 550 and enterprise network(s) 570 can embody, at least in part, a service network(s) like IP multimedia subsystem (IMS). Based on radio technology layer(s) available in technology resource(s) or radio access network 520, PS gateway node(s) 518 can generate packet data protocol contexts when a data session is established; other data structures that facilitate routing of packetized data also can be generated. To that end, in an aspect, PS gateway node(s) 518 can comprise a tunnel interface (e.g., tunnel termination gateway (TTG) in 3GPP UMTS network(s) (not shown)) which can facilitate packetized communication with disparate wireless network(s), such as Wi-Fi networks.

In embodiment 500, mobile network platform 510 also comprises serving node(s) 516 that, based upon available radio technology layer(s) within technology resource(s) in the radio access network 520, convey the various packetized flows of data streams received through PS gateway node(s) 518. It is to be noted that for technology resource(s) that rely primarily on CS communication, server node(s) can deliver traffic without reliance on PS gateway node(s) 518; for example, server node(s) can embody at least in part a mobile switching center. As an example, in a 3GPP UMTS network, serving node(s) 516 can be embodied in serving GPRS support node(s) (SGSN).

For radio technologies that exploit packetized communication, server(s) 514 in mobile network platform 510 can execute numerous applications that can generate multiple disparate packetized data streams or flows, and manage (e.g., schedule, queue, format . . . ) such flows. Such application(s) can comprise add-on features to standard services (for example, provisioning, billing, customer support . . . ) provided by mobile network platform 510. Data streams (e.g., content(s) that are part of a voice call or data session) can be conveyed to PS gateway node(s) 518 for authorization/authentication and initiation of a data session, and to serving node(s) 516 for communication thereafter. In addition to application server, server(s) 514 can comprise utility server(s), a utility server can comprise a provisioning server, an operations and maintenance server, a security server that can implement at least in part a certificate authority and firewalls as well as other security mechanisms, and the like. In an aspect, security server(s) secure communication served through mobile network platform 510 to ensure network's operation and data integrity in addition to authorization and authentication procedures that CS gateway node(s) 512 and PS gateway node(s) 518 can enact. Moreover, provisioning server(s) can provision services from external network(s) like networks operated by a disparate service provider; for instance, WAN 550 or Global Positioning System (GPS) network(s) (not shown). Provisioning server(s) can also provision coverage through networks associated to mobile network platform 510 (e.g., deployed and operated by the same service provider), such as the distributed antennas networks shown in FIG. 1(s) that enhance wireless service coverage by providing more network coverage.

It is to be noted that server(s) 514 can comprise one or more processors configured to confer at least in part the functionality of mobile network platform 510. To that end, the one or more processor can execute code instructions stored in memory 530, for example. It is should be appreciated that server(s) 514 can comprise a content manager, which operates in substantially the same manner as described hereinbefore.

In example embodiment 500, memory 530 can store information related to operation of mobile network platform 510. Other operational information can comprise provisioning information of mobile devices served through mobile network platform 510, subscriber databases; application intelligence, pricing schemes, e.g., promotional rates, flat-rate programs, couponing campaigns; technical specification(s) consistent with telecommunication protocols for operation of disparate radio, or wireless, technology layers; and so forth. Memory 530 can also store information from at least one of telephony network(s) 540, WAN 550, SS7 network 560, or enterprise network(s) 570. In an aspect, memory 530 can be, for example, accessed as part of a data store component or as a remotely connected memory store.

In order to provide a context for the various aspects of the disclosed subject matter, FIG. 5, and the following discussion, are intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter can be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a computer program that runs on a computer and/or computers, those skilled in the art will recognize that the disclosed subject matter also can be implemented in combination with other program modules. Generally, program modules comprise routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types.

Turning now to FIG. 6, an illustrative embodiment of a communication device 600 is shown. The communication device 600 can serve as an illustrative embodiment of devices such as data terminals 114, mobile devices 124, vehicle 126, display devices 144 or other client devices for communication via either communications network 125. For example, computing device 600 can facilitate in whole or in part a communication device with an expired subscription for services to renew the subscription for services, subscribe to different services, or migrate to a different mobile network to subscribe for services. Further, the network devices, network nodes, communication devices, mobile devices, sensors, smart power meters, IoT devices, and web server can comprise the communication device 600.

The communication device 600 can comprise a wireline and/or wireless transceiver 602 (herein transceiver 602), a user interface (UI) 604, a power supply 614, a location receiver 616, a motion sensor 618, an orientation sensor 620, and a controller 606 for managing operations thereof. The transceiver 602 can support short-range or long-range wireless access technologies such as Bluetooth®, ZigBee®, WiFi, DECT, or cellular communication technologies, just to mention a few (Bluetooth® and ZigBee® are trademarks registered by the Bluetooth® Special Interest Group and the ZigBee® Alliance, respectively). Cellular technologies can include, for example, CDMA-1×, UMTS/HSDPA, GSM/GPRS, TDMA/EDGE, EV/DO, WiMAX, SDR, LTE, as well as other next generation wireless communication technologies as they arise. The transceiver 602 can also be adapted to support circuit-switched wireline access technologies (such as PSTN), packet-switched wireline access technologies (such as TCP/IP, VoIP, etc.), and combinations thereof.

The UI 604 can include a depressible or touch-sensitive keypad 608 with a navigation mechanism such as a roller ball, a joystick, a mouse, or a navigation disk for manipulating operations of the communication device 600. The keypad 608 can be an integral part of a housing assembly of the communication device 600 or an independent device operably coupled thereto by a tethered wireline interface (such as a USB cable) or a wireless interface supporting for example Bluetooth®. The keypad 608 can represent a numeric keypad commonly used by phones, and/or a QWERTY keypad with alphanumeric keys. The UI 604 can further include a display 610 such as monochrome or color LCD (Liquid Crystal Display), OLED (Organic Light Emitting Diode) or other suitable display technology for conveying images to an end user of the communication device 600. In an embodiment where the display 610 is touch-sensitive, a portion or all of the keypad 608 can be presented by way of the display 610 with navigation features.

The display 610 can use touch screen technology to also serve as a user interface for detecting user input. As a touch screen display, the communication device 600 can be adapted to present a user interface having graphical user interface (GUI) elements that can be selected by a user with a touch of a finger. The display 610 can be equipped with capacitive, resistive or other forms of sensing technology to detect how much surface area of a user's finger has been placed on a portion of the touch screen display. This sensing information can be used to control the manipulation of the GUI elements or other functions of the user interface. The display 610 can be an integral part of the housing assembly of the communication device 600 or an independent device communicatively coupled thereto by a tethered wireline interface (such as a cable) or a wireless interface.

The UI 604 can also include an audio system 612 that utilizes audio technology for conveying low volume audio (such as audio heard in proximity of a human ear) and high volume audio (such as speakerphone for hands free operation). The audio system 612 can further include a microphone for receiving audible signals of an end user. The audio system 612 can also be used for voice recognition applications. The UI 604 can further include an image sensor 613 such as a charged coupled device (CCD) camera for capturing still or moving images.

The power supply 614 can utilize common power management technologies such as replaceable and rechargeable batteries, supply regulation technologies, and/or charging system technologies for supplying energy to the components of the communication device 600 to facilitate long-range or short-range portable communications. Alternatively, or in combination, the charging system can utilize external power sources such as DC power supplied over a physical interface such as a USB port or other suitable tethering technologies.

The location receiver 616 can utilize location technology such as a global positioning system (GPS) receiver capable of assisted GPS for identifying a location of the communication device 600 based on signals generated by a constellation of GPS satellites, which can be used for facilitating location services such as navigation. The motion sensor 618 can utilize motion sensing technology such as an accelerometer, a gyroscope, or other suitable motion sensing technology to detect motion of the communication device 600 in three-dimensional space. The orientation sensor 620 can utilize orientation sensing technology such as a magnetometer to detect the orientation of the communication device 600 (north, south, west, and east, as well as combined orientations in degrees, minutes, or other suitable orientation metrics).

The communication device 600 can use the transceiver 602 to also determine a proximity to a cellular, WiFi, Bluetooth®, or other wireless access points by sensing techniques such as utilizing a received signal strength indicator (RSSI) and/or signal time of arrival (TOA) or time of flight (TOF) measurements. The controller 606 can utilize computing technologies such as a microprocessor, a digital signal processor (DSP), programmable gate arrays, application specific integrated circuits, and/or a video processor with associated storage memory such as Flash, ROM, RAM, SRAM, DRAM or other storage technologies for executing computer instructions, controlling, and processing data supplied by the aforementioned components of the communication device 600.

Other components not shown in FIG. 6 can be used in one or more embodiments of the subject disclosure. For instance, the communication device 600 can include a slot for adding or removing an identity module such as a Subscriber Identity Module (SIM) card or Universal Integrated Circuit Card (UICC). SIM or UICC cards can be used for identifying subscriber services, executing programs, storing subscriber data, and so on.

The terms “first,” “second,” “third,” and so forth, as used in the claims, unless otherwise clear by context, is for clarity only and doesn't otherwise indicate or imply any order in time. For instance, “a first determination,” “a second determination,” and “a third determination,” does not indicate or imply that the first determination is to be made before the second determination, or vice versa, etc.

In the subject specification, terms such as “store,” “storage,” “data store,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components described herein can be either volatile memory or nonvolatile memory, or can comprise both volatile and nonvolatile memory, by way of illustration, and not limitation, volatile memory, non-volatile memory, disk storage, and memory storage. Further, nonvolatile memory can be included in read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable ROM (EEPROM), or flash memory. Volatile memory can comprise random access memory (RAM), which acts as external cache memory. By way of illustration and not limitation, RAM is available in many forms such as synchronous RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), Synchlink DRAM (SLDRAM), and direct Rambus RAM (DRRAM). Additionally, the disclosed memory components of systems or methods herein are intended to comprise, without being limited to comprising, these and any other suitable types of memory.

Moreover, it will be noted that the disclosed subject matter can be practiced with other computer system configurations, comprising single-processor or multiprocessor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., PDA, phone, smartphone, watch, tablet computers, netbook computers, etc.), microprocessor-based or programmable consumer or industrial electronics, and the like. The illustrated aspects can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network; however, some if not all aspects of the subject disclosure can be practiced on stand-alone computers. In a distributed computing environment, program modules can be located in both local and remote memory storage devices.

In one or more embodiments, information regarding use of services can be generated including services being accessed, media consumption history, user preferences, and so forth. This information can be obtained by various methods including user input, detecting types of communications (e.g., video content vs. audio content), analysis of content streams, sampling, and so forth. The generating, obtaining and/or monitoring of this information can be responsive to an authorization provided by the user. In one or more embodiments, an analysis of data can be subject to authorization from user(s) associated with the data, such as an opt-in, an opt-out, acknowledgement requirements, notifications, selective authorization based on types of data, and so forth.

Some of the embodiments described herein can also employ artificial intelligence (AI) to facilitate automating one or more features described herein. The embodiments (e.g., in connection with automatically managing devices through use of blocks of operational profiles) can employ various AI-based schemes for carrying out various embodiments thereof. Moreover, the classifier can be employed to determine a ranking or priority of each cell site of the acquired network. A classifier is a function that maps an input attribute vector, x=(x1, x2, x3, x4, . . . , xn), to a confidence that the input belongs to a class, that is, f(x)=confidence (class). Such classification can employ a probabilistic and/or statistical-based analysis (e.g., factoring into the analysis utilities and costs) to determine or infer an action that a user desires to be automatically performed. A support vector machine (SVM) is an example of a classifier that can be employed. The SVM operates by finding a hypersurface in the space of possible inputs, which the hypersurface attempts to split the triggering criteria from the non-triggering events. Intuitively, this makes the classification correct for testing data that is near, but not identical to training data. Other directed and undirected model classification approaches comprise, e.g., naïve Bayes, Bayesian networks, decision trees, neural networks, fuzzy logic models, and probabilistic classification models providing different patterns of independence can be employed. Classification as used herein also is inclusive of statistical regression that is utilized to develop models of priority.

As will be readily appreciated, one or more of the embodiments can employ classifiers that are explicitly trained (e.g., via a generic training data) as well as implicitly trained (e.g., via observing UE behavior, operator preferences, historical information, receiving extrinsic information). For example, SVMs can be configured via a learning or training phase within a classifier constructor and feature selection module. Thus, the classifier(s) can be used to automatically learn and perform a number of functions, including but not limited to determining according to predetermined criteria which of the acquired cell sites will benefit a maximum number of subscribers and/or which of the acquired cell sites will add minimum value to the existing communication network coverage, etc.

As used in some contexts in this application, in some embodiments, the terms “component,” “system” and the like are intended to refer to, or comprise, a computer-related entity or an entity related to an operational apparatus with one or more specific functionalities, wherein the entity can be either hardware, a combination of hardware and software, software, or software in execution. As an example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an executable, a thread of execution, computer-executable instructions, a program, and/or a computer. By way of illustration and not limitation, both an application running on a server and the server can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers. In addition, these components can execute from various computer readable media having various data structures stored thereon. The components may communicate via local and/or remote processes such as in accordance with a signal having one or more data packets (e.g., data from one component interacting with another component in a local system, distributed system, and/or across a network such as the Internet with other systems via the signal). As another example, a component can be an apparatus with specific functionality provided by mechanical parts operated by electric or electronic circuitry, which is operated by a software or firmware application executed by a processor, wherein the processor can be internal or external to the apparatus and executes at least a part of the software or firmware application. As yet another example, a component can be an apparatus that provides specific functionality through electronic components without mechanical parts, the electronic components can comprise a processor therein to execute software or firmware that confers at least in part the functionality of the electronic components. While various components have been illustrated as separate components, it will be appreciated that multiple components can be implemented as a single component, or a single component can be implemented as multiple components, without departing from example embodiments.

Further, the various embodiments can be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware or any combination thereof to control a computer to implement the disclosed subject matter. The term “article of manufacture” as used herein is intended to encompass a computer program accessible from any computer-readable device or computer-readable storage/communications media. For example, computer readable storage media can include, but are not limited to, magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips), optical disks (e.g., compact disk (CD), digital versatile disk (DVD)), smart cards, and flash memory devices (e.g., card, stick, key drive). Of course, those skilled in the art will recognize many modifications can be made to this configuration without departing from the scope or spirit of the various embodiments.

In addition, the words “example” and “exemplary” are used herein to mean serving as an instance or illustration. Any embodiment or design described herein as “example” or “exemplary” is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, use of the word example or exemplary is intended to present concepts in a concrete fashion. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or”. That is, unless specified otherwise or clear from context, “X employs A or B” is intended to mean any of the natural inclusive permutations. That is, if X employs A; X employs B; or X employs both A and B, then “X employs A or B” is satisfied under any of the foregoing instances. In addition, the articles “a” and “an” as used in this application and the appended claims should generally be construed to mean “one or more” unless specified otherwise or clear from context to be directed to a singular form.

Moreover, terms such as “user equipment,” “mobile station,” “mobile,” subscriber station,” “access terminal,” “terminal,” “handset,” “mobile device” (and/or terms representing similar terminology) can refer to a wireless device utilized by a subscriber or user of a wireless communication service to receive or convey data, control, voice, video, sound, gaming or substantially any data-stream or signaling-stream. The foregoing terms are utilized interchangeably herein and with reference to the related drawings.

Furthermore, the terms “user,” “subscriber,” “customer,” “consumer” and the like are employed interchangeably throughout, unless context warrants particular distinctions among the terms. It should be appreciated that such terms can refer to human entities or automated components supported through artificial intelligence (e.g., a capacity to make inference based, at least, on complex mathematical formalisms), which can provide simulated vision, sound recognition and so forth.

As employed herein, the term “processor” can refer to substantially any computing processing unit or device comprising, but not limited to comprising, single-core processors; single-processors with software multithread execution capability; multi-core processors; multi-core processors with software multithread execution capability; multi-core processors with hardware multithread technology; parallel platforms; and parallel platforms with distributed shared memory. Additionally, a processor can refer to an integrated circuit, an application specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a programmable logic controller (PLC), a complex programmable logic device (CPLD), a discrete gate or transistor logic, discrete hardware components or any combination thereof designed to perform the functions described herein. Processors can exploit nano-scale architectures such as, but not limited to, molecular and quantum-dot based transistors, switches and gates, in order to optimize space usage or enhance performance of user equipment. A processor can also be implemented as a combination of computing processing units.

As used herein, terms such as “data storage,” data storage,” “database,” and substantially any other information storage component relevant to operation and functionality of a component, refer to “memory components,” or entities embodied in a “memory” or components comprising the memory. It will be appreciated that the memory components or computer-readable storage media, described herein can be either volatile memory or nonvolatile memory or can include both volatile and nonvolatile memory.

What has been described above includes mere examples of various embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing these examples, but one of ordinary skill in the art can recognize that many further combinations and permutations of the present embodiments are possible. Accordingly, the embodiments disclosed and/or claimed herein are intended to embrace all such alterations, modifications and variations that fall within the spirit and scope of the appended claims. Furthermore, to the extent that the term “includes” is used in either the detailed description or the claims, such term is intended to be inclusive in a manner similar to the term “comprising” as “comprising” is interpreted when employed as a transitional word in a claim.

In addition, a flow diagram may include a “start” and/or “continue” indication. The “start” and “continue” indications reflect that the steps presented can optionally be incorporated in or otherwise used in conjunction with other routines. In this context, “start” indicates the beginning of the first step presented and may be preceded by other activities not specifically shown. Further, the “continue” indication reflects that the steps presented may be performed multiple times and/or may be succeeded by other activities not specifically shown. Further, while a flow diagram indicates a particular ordering of steps, other orderings are likewise possible provided that the principles of causality are maintained.

As may also be used herein, the term(s) “operably coupled to”, “coupled to”, and/or “coupling” includes direct coupling between items and/or indirect coupling between items via one or more intervening items. Such items and intervening items include, but are not limited to, junctions, communication paths, components, circuit elements, circuits, functional blocks, and/or devices. As an example of indirect coupling, a signal conveyed from a first item to a second item may be modified by one or more intervening items by modifying the form, nature or format of information in a signal, while one or more elements of the information in the signal are nevertheless conveyed in a manner than can be recognized by the second item. In a further example of indirect coupling, an action in a first item can cause a reaction on the second item, as a result of actions and/or reactions in one or more intervening items. Although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement which achieves the same or similar purpose may be substituted for the embodiments described or shown by the subject disclosure. The subject disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, can be used in the subject disclosure. For instance, one or more features from one or more embodiments can be combined with one or more features of one or more other embodiments. In one or more embodiments, features that are positively recited can also be negatively recited and excluded from the embodiment with or without replacement by another structural and/or functional feature. The steps or functions described with respect to the embodiments of the subject disclosure can be performed in any order. The steps or functions described with respect to the embodiments of the subject disclosure can be performed alone or in combination with other steps or functions of the subject disclosure, as well as from other embodiments or from other steps that have not been described in the subject disclosure. Further, more than or less than all of the features described with respect to an embodiment can also be utilized. 

What is claimed is:
 1. A mobile communication device comprising: a processing system including a processor; and a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations, the operations comprising: coordinating assignment of each operational profile of a pool of operational profiles so as to prevent simultaneous use of a same operational profile by more than one device of a plurality of devices at a same time, the coordinating comprising: assigning a first operational profile of the pool of operational profiles to a first device of the plurality of devices; and assigning a second, different, operational profile of the pool of operational profiles to a second device of the plurality of devices, the first device being a separate device from the second device, and the first operational profile assigned to the first device facilitating disabling for the second device of services associated with the second operational profile; facilitating first provision of the first operational profile on the first device, the first operational profile having a time to live period, the first operational profile being converted at an expiration of the time to live period to a bootstrap profile, and the bootstrap profile providing limited connectivity solely for a purpose of converting back to the first operational profile; and facilitating second provision of the second operational profile on the second device.
 2. The mobile communication device of claim 1, wherein the mobile communication device comprises a smartphone, a tablet, a laptop computer or a notebook computer.
 3. The mobile communication device of claim 1, wherein each of the plurality of devices comprises an Internet of Things (IoT) device.
 4. The mobile communication device of claim 1, wherein each of the plurality of devices comprises a communication device.
 5. The mobile communication device of claim 1, wherein: the facilitating the first provision of the first operational profile on the first device comprises providing to the first device, by the mobile communication device, the first operational profile; and the facilitating the second provision of the second operational profile on the second device comprises providing to the second device, by the mobile communication device, the second operational profile.
 6. The mobile communication device of claim 5, wherein: the providing to the first device, by the mobile communication device, the first operational profile comprises providing the first operational profile to the first device via the Internet, providing the first operational profile to the first device via a first near field communication path, or any combination thereof; and the providing to the second device, by the mobile communication device, the second operational profile comprises providing the second operational profile to the second device via the Internet, providing the second operational profile to the second device via a second near field communication path, or any combination thereof.
 7. The mobile communication device of claim 6, wherein the operations further comprise: receiving by the mobile communication device, from a server that is part of a communications network operated by a network provider, the first operational profile; and receiving by the mobile communication device, from the server, the second operational profile; wherein the providing to the first device, by the mobile communication device, the first operational profile comprises providing to the first device, by the mobile communication device, the first operational profile that is received from the server; and wherein the providing to the second device, by the mobile communication device, the second operational profile comprises providing to the second device, by the mobile communication device, the second operational profile that is received from the server.
 8. The mobile communication device of claim 1, wherein: the facilitating the first provision of the first operational profile on the first device comprises providing a first message to a server that is part of a communications network operated by a network provider to instruct the server to provide the first operational profile to the first device; and the facilitating the second provision of the second operational profile on the second device comprises providing a second message to the server to instruct the server to provide the second operational profile to the second device.
 9. The mobile communication device of claim 8, wherein: the server provides the first operational profile to the first device via the Internet; and the server provides the second operational profile to the second device via the Internet.
 10. The mobile communication device of claim 9, wherein: the server provides the first operational profile to the first device via a first over-the-air (OTA) communication; and the server provides the second operational profile to the second device via a second OTA communication.
 11. The mobile communication device of claim 1, wherein the time to live period is associated with an activation of the first operational profile on the first device, and wherein the operations further comprise: un-assigning the first operational profile from the first device, wherein the un-assigning is responsive to the expiration of the time to live period.
 12. The mobile communication device of claim 11, wherein the operations further comprise: re-assigning the first operational profile to a third device of the plurality of devices; and facilitating third provision of the first operational profile on the third device.
 13. A non-transitory machine-readable medium comprising executable instructions that, when executed by a processing system of a mobile communication device including a processor, facilitate performance of operations, the operations comprising: receiving, a list of a plurality of operational profiles that are to be shared by a plurality of IoT devices; and coordinating assignment of each operational profile of the plurality of operational profiles so as to prevent simultaneous use of a same operational profile by more than one IoT device of the plurality of IoT devices at a same time, the coordinating comprising: providing, based upon each operational profile being assigned to a different IoT device of the plurality of IoT devices, a first operational profile of the plurality of operational profiles to a first IoT device of the plurality of IoT devices, the first operational profile having a time to live period, the first operational profile being converted at an expiration of the time to live period to a bootstrap profile, and the bootstrap profile providing limited connectivity solely for a purpose of converting back to the first operational profile; and providing, based upon each operational profile being assigned to a different IoT device of the plurality of IoT devices, a second operational profile of the plurality of operational profiles to a second IoT device of the plurality of IoT devices, the first IoT device being a separate device from the second IoT device, and the first operational profile provided to the first IoT device facilitating disabling for the second IoT device of services associated with the second operational profile.
 14. The non-transitory machine-readable medium of claim 13, wherein the mobile communication device comprises a smartphone, a tablet, a laptop computer or a notebook computer.
 15. The non-transitory machine-readable medium of claim 13, wherein each operational profile of the plurality of operational profiles is assigned to one IoT device by the mobile communication device.
 16. The non-transitory machine-readable medium of claim 13, wherein one or more of the plurality of IoT devices comprises a respective sensor.
 17. A method comprising: receiving, by a processing system of a mobile communication device including a processor, a list identifying a plurality of operational profiles that are to be shared by a plurality of Internet of Things (IoT) devices; and coordinating assignment, by the processing system, of each operational profile of the plurality of operational profiles so as to prevent simultaneous use of a same operational profile by more than one IoT device of the plurality of IoT devices at a same time, the coordinating comprising: providing, by the processing system, based upon the list, a first operational profile of the plurality of operational profiles to a first IoT device of the plurality of IoT devices, the providing of the first operational profile enabling use by the first IoT device of the first operational profile, the first operational profile having a time to live period, the first operational profile being converted at an expiration of the time to live period to a bootstrap profile, and the bootstrap profile providing limited connectivity solely for a purpose of converting back to the first operational profile; and providing, by the processing system, based upon the list, a second operational profile of the plurality of operational profiles to the first IoT device, the providing of the second operational profile enabling the first IoT device to send to a second IoT device the second operational profile for use by the second IoT device, the first IoT device being a separate device from the second IoT device, and the first operational profile provided to the first IoT device facilitating disabling for the second IoT device of services associated with the second operational profile.
 18. The method of claim 17, wherein the mobile communication device comprises a smartphone, a tablet, a laptop computer or a notebook computer.
 19. The method of claim 17, wherein: the providing of the first operational profile enables use by the first IoT device of the first operational profile in order to communicate with a communications network operated by a network provider; and the second operational profile that is sent from the first IoT device to the second IoT device enables use by the second IoT device of the second operational profile in order to communicate with the communications network.
 20. The method of claim 17, wherein one or more of the plurality of IoT devices comprises a respective sensor. 